Ip address allocation in evolved wireless networks

ABSTRACT

A networking system includes a first wireless network module that transmits a request to attach to a network and a second wireless network module. The second wireless network module receives the request, determines whether the first wireless network module requires an IP address based on the request, and selectively allocates an IP address to the first wireless network module based on the determination.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.60/908,823, filed on Mar. 29, 2007, which is incorporated herein byreference in its entirety.

FIELD

The present disclosure relates to IP address allocation in evolvedwireless networks.

BACKGROUND

The background description provided herein is for the purpose ofgenerally presenting the context of the disclosure. Work of thepresently named inventors, to the extent it is described in thisbackground section, as well as aspects of the description that may nototherwise qualify as prior art at the time of filing, are neitherexpressly nor impliedly admitted as prior art against the presentdisclosure.

In a wireless network (such as, for example, a 3^(rd) GenerationPartnership Project (3GPP) evolved wireless network, a wireless terminalmay request to attach to the wireless network via an attach procedure.The wireless terminal may include user equipment (UE) in the 3GPPwireless network. For example, the wireless terminal may include amobile phone, and the wireless network may be the cellular network of amobile phone operator. Conversely, the wireless terminal may include alaptop computer or other mobile computing device, and the wirelessnetwork may be a local area network (LAN) or Internet service provider(ISP). The wireless network allocates an IP address to the wirelessterminal during the attach procedure.

Referring now to FIGS. 1-3, exemplary wireless networks that mayimplement the attach procedure are shown. As shown in FIG. 1, a homenetwork 102 receives packets from and sends packets to a distributedcommunications system 104 such as the Internet. A wireless terminal 106wirelessly connects to the home network 102. As shown in FIG. 2, thehome network 102 is connected to one or more visited networks 110. Forexample only, FIG. 2 depicts three visited networks 110-1, 110-2 and110-3. In various implementations, the visited networks 110 may be thenetworks of other service providers, including service providers inother countries. A mobile wireless terminal 120 includes mobilityfeatures that allow the mobile wireless terminal 120 to communicate withthe visited networks 110.

Referring now to FIG. 3, a functional block diagram depicts a wirelesscommunications system that provides proxy mobility to the wirelessterminal 106. A home network 150 communicates with visited networks160-1, 160-2, and 160-3. The visited networks 160 provide transparentmobility to wireless terminals, such as the wireless terminal 106, thathave not been updated to include mobility functionality.

As described above with respect to FIGS. 1-3, the wireless terminal mayattempt to establish a link with one of the home network 102, a visitednetwork 110, and/or a visited network with mobility 160 via an attachprocedure. Attachment to visited networks and visited networks withmobility are described in more detail in U.S. patent application Ser.No. 12/009,725, filed Jan. 22, 2008, which is incorporated herein byreference.

Referring now to FIG. 4, a timeline of steps performed when the wirelessterminal 106 connects to the network 102 (i.e. an attach procedure) isshown. The attach procedure 200 includes interaction between thewireless terminal 106 and one or more nodes of the network 102,including, but not limited to, a mobility management entity (MME) 202, aserving SAE (system architecture evolution) gateway 204, a packet datanetwork (PDN) SAE gateway 206, a policy and charging rules function(PCRF) 208, and a home subscriber server (HSS) 210. For example only,the wireless terminal 106 may include a UE device and an enhanced orevolved node B (eNB) wireless base station.

The wireless terminal 106 performs authentication and identificationwith the network 102. This may include communicating with an Access,Authentication, and Accounting (AAA) server. During authentication andidentification, the wireless terminal 106 transmits an attach request tothe MME 202. The MME 202 requests an identity of the wireless terminal106 and authenticates the identity with the HSS 210. Uponauthentication, the PDN SAE gateway 206 allocates an Internet protocol(IP) address to the wireless terminal 106 and accepts the attachrequest. The wireless terminal 106 completes the attach. The attachprocedure 200 may include other network-side steps unrelated to IPaddress allocation, such as clearing previous bearer context requestsand updating locations.

SUMMARY

A networking system comprises a first wireless network module thattransmits a request to attach to a network and a second wireless networkmodule. The second wireless network module receives the request,determines whether the first wireless network module requires an IPaddress based on the request, and selectively allocates an IP address tothe first wireless network module based on the determination.

In other features, the request includes an indication that the firstwireless network module requires an IP address. The second wirelessnetwork module allocates an IP address to the first wireless networkmodule based on the request. The request includes an indication that thewireless network module does not require an IP address. The secondwireless network module does not allocate an IP address to the firstwireless network module. The first wireless network module attaches tothe network without receiving an IP address. After attaching to thenetwork, the first wireless network module obtains an IP address from athird wireless network module. The first wireless network modulemodifies a bearer context based on the IP address obtained from thethird wireless network module.

In other features, the second wireless network module retrievessubscriber data associated with the first wireless network module basedon the request. A database stores the subscriber data. The secondwireless network module determines whether to allocate an IP address tothe first wireless network module based on the subscriber data. Thesubscriber data indicates whether the first wireless network module isone of an integrated wireless terminal and a non-integrated wirelessterminal. The subscriber data indicates whether the first wirelessnetwork module requires IP address allocation during an attachprocedure.

In other features, the network comprises a 3^(rd) Generation PartnershipProject (3GPP) evolved wireless network. The first wireless networkmodule comprises at least one of a mobile telephone and a laptopcomputer. The second wireless network module comprises at least one of amobility management entity (MME), a gateway, and a home subscriberserver (HSS) in a 3^(rd) Generation Partnership Project (3GPP) evolvedwireless network. The second wireless network module creates a bearercontext request that indicates whether the first wireless network modulerequires IP address allocation.

A networking method comprises transmitting a request to attach to anetwork from a first wireless network module, receiving the request at asecond wireless network module, determining whether the first wirelessnetwork module requires an IP address based on the request, andselectively allocating an IP address to the first wireless networkmodule based on the determination.

In other features, the request includes an indication that the wirelessnetwork module requires an IP address. The method further comprisesallocating an IP address to the first wireless network module based onthe request. The request includes an indication that the wirelessnetwork module does not require an IP address. The first wirelessnetwork module is not allocated an IP address. The first wirelessnetwork module attaches to the network without receiving an IP address.After attaching to the network, the first wireless network moduleobtains an IP address from a third wireless network module. The methodfurther comprises modifying a bearer context based on the IP addressobtained from the third wireless network module.

In other features, the method further comprises retrieving subscriberdata associated with the first wireless network module based on therequest. The method further comprises storing the subscriber data in adatabase. The method further comprises determining whether to allocatean IP address to the first wireless network module based on thesubscriber data. The subscriber data indicates whether the firstwireless network module is one of an integrated wireless terminal and anon-integrated wireless terminal. The subscriber data indicates whetherthe first wireless network module requires IP address allocation duringan attach procedure.

In other features, the network comprises a 3^(rd) Generation PartnershipProject (3GPP) evolved wireless network. The first wireless networkmodule comprises at least one of a mobile telephone and a laptopcomputer. The second wireless network module comprises at least one of amobility management entity (MME), a gateway, and a home subscriberserver (HSS) in a 3^(rd) Generation Partnership Project (3GPP) evolvedwireless network. The method further comprises creating a bearer contextrequest that indicates whether the first wireless network modulerequires IP address allocation.

A networking system comprises first wireless network means fortransmitting a request to attach to a network and second wirelessnetwork means for receiving the request, for determining whether thefirst wireless network means requires an IP address based on therequest, and for selectively allocates an IP address to the firstwireless network means based on the determination.

In other features, the request includes an indication that the firstwireless network means requires an IP address. The second wirelessnetwork means allocates an IP address to the first wireless networkmeans based on the request. The request includes an indication that thefirst wireless network means does not require an IP address. The secondwireless network means does not allocate an IP address to the firstwireless network means. The first wireless network means attaches to thenetwork without receiving an IP address. After attaching to the network,the first wireless network means obtains an IP address from thirdwireless network means for allocating an IP address. The first wirelessnetwork means modifies a bearer context based on the IP address obtainedfrom the third wireless network means.

In other features, the second wireless network means retrievessubscriber data associated with the first wireless network means basedon the request. A database stores the subscriber data. The secondwireless network means determines whether to allocate an IP address tothe first wireless network means based on the subscriber data. Thesubscriber data indicates whether the first wireless network means isone of an integrated wireless terminal and a non-integrated wirelessterminal. The subscriber data indicates whether the first wirelessnetwork means requires IP address allocation during an attach procedure.

In other features, the network comprises a 3^(rd) Generation PartnershipProject (3GPP) evolved wireless network. The first wireless networkmeans comprises at least one of a mobile telephone and a laptopcomputer. The second wireless network means comprises at least one of amobility management entity (MME), a gateway, and a home subscriberserver (HSS) in a 3^(rd) Generation Partnership Project (3GPP) evolvedwireless network. The second wireless network means creates a bearercontext request that indicates whether the first wireless network meansrequires IP address allocation.

A computer program stored on a computer-readable medium for use by aprocessor for operating a network comprises transmitting a request toattach to a network from a first wireless network module, receiving therequest at a second wireless network module, determining whether thefirst wireless network module requires an IP address based on therequest, and selectively allocating an IP address to the first wirelessnetwork module based on the determination.

In other features, the request includes an indication that the wirelessnetwork module requires an IP address. The computer program furthercomprises allocating an IP address to the first wireless network modulebased on the request. The request includes an indication that thewireless network module does not require an IP address. The firstwireless network module is not allocated an IP address. The firstwireless network module attaches to the network without receiving an IPaddress. After attaching to the network, the first wireless networkmodule obtains an IP address from a third wireless network module. Thecomputer program further comprises modifying a bearer context based onthe IP address obtained from the third wireless network module.

In other features, the computer program further comprises retrievingsubscriber data associated with the first wireless network module basedon the request. The computer program further comprises storing thesubscriber data in a database. The computer program further comprisesdetermining whether to allocate an IP address to the first wirelessnetwork module based on the subscriber data. The subscriber dataindicates whether the first wireless network module is one of anintegrated wireless terminal and a non-integrated wireless terminal. Thesubscriber data indicates whether the first wireless network modulerequires IP address allocation during an attach procedure.

In other features, the network comprises a 3^(rd) Generation PartnershipProject (3GPP) evolved wireless network. The first wireless networkmodule comprises at least one of a mobile telephone and a laptopcomputer. The second wireless network module comprises at least one of amobility management entity (MME), a gateway, and a home subscriberserver (HSS) in a 3^(rd) Generation Partnership Project (3GPP) evolvedwireless network. The computer program further comprises creating abearer context request that indicates whether the first wireless networkmodule requires IP address allocation.

In still other features, the systems and methods described above areimplemented by a computer program executed by one or more processors.The computer program can reside on a computer readable medium such asbut not limited to memory, nonvolatile data storage, and/or othersuitable tangible storage mediums.

Further areas of applicability of the present disclosure will becomeapparent from the detailed description and the drawings. The detaileddescription and specific examples are intended for purposes ofillustration only and are not intended to limit the scope of thedisclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will become more fully understood from thedetailed description and the accompanying drawings, wherein:

FIG. 1 is a functional block diagram of a wireless communications systemaccording to the prior art;

FIG. 2 is a functional block diagram of a wireless communications systemoffering mobility according to the prior art;

FIG. 3 is a functional block diagram of a wireless communications systemthat provides proxy mobility to a wireless terminal according to theprior art;

FIG. 4 illustrates a wireless terminal attach procedure according to theprior art;

FIG. 5 illustrates a wireless terminal attach procedure wherein thewireless terminal requires IP address allocation;

FIG. 6 illustrates a wireless terminal attach procedure wherein thewireless terminal does not require IP address allocation;

FIG. 7 is a flow diagram illustrating steps of an attach procedure;

FIG. 8 illustrates a wireless terminal attach procedure wherein anetwork allocates an IP address based on subscriber data;

FIG. 9 illustrates a wireless terminal attach procedure wherein anetwork does not allocate an IP address based on subscriber data;

FIG. 10 is a flow diagram illustrating steps of an attach procedurebased on subscriber data;

FIG. 11A is a functional block diagram of a hard disk drive;

FIG. 11B is a functional block diagram of a digital versatile disc (DVD)drive;

FIG. 11C is a functional block diagram of a high definition television;

FIG. 11D is a functional block diagram of a vehicle;

FIG. 11E is a functional block diagram of a cellular phone;

FIG. 11F is a functional block diagram of a set top box; and

FIG. 11G is a functional block diagram of a mobile device.

DETAILED DESCRIPTION

The following description is merely exemplary in nature and is in no wayintended to limit the disclosure, its application, or uses. For purposesof clarity, the same reference numbers will be used in the drawings toidentify similar elements. As used herein, the phrase at least one of A,B, and C should be construed to mean a logical (A or B or C), using anon-exclusive logical or. Steps within a method may be executed indifferent order or concurrently without altering the principles of thepresent disclosure.

As used herein, the term module refers to an Application SpecificIntegrated Circuit (ASIC), an electronic circuit, a processor (shared,dedicated, or group) and memory that execute one or more software orfirmware programs, a combinational logic circuit, and/or other suitablecomponents that provide the described functionality.

A wireless terminal is automatically allocated an IP address during anattach procedure in, for example, a 3GPP evolved wireless networkregardless of terminal type. For example, wireless terminals that attachto the wireless network may include integrated and non-integratedterminals. Integrated terminals include, for example, cellular phones,which may require IP address allocation during the attach procedure.Non-integrated terminals include, for example, laptop computers with awireless module (e.g. a PCMCIA card). Non-integrated terminals mayrequire IP address allocation after the attach procedure is completedvia an alternative allocation method such as DHCP (dynamic hostconfiguration protocol).

When a non-integrated wireless terminal attaches to the wirelessnetwork, the wireless module automatically receives an IP address viathe attach procedure. For example, the wireless network typically doesnot differentiate between wireless terminal types during the attachprocedure and automatically allocates the IP address in response to theattach request. An operating system of the non-integrated wirelessterminal may not be aware of the assigned IP address and may acquire asecond IP address via an alternative method. Consequently, thenon-integrated wireless terminal receives two IP addresses.

During an attach procedure in one implementation, the wireless networkselectively allocates an IP address to the wireless terminal based onwireless terminal type. In such an implementation, instead ofautomatically allocating an IP address to the wireless terminal, thewireless network determines whether the wireless terminal requires an IPaddress during the attach procedure and selectively allocates an IPaddress accordingly. Consequently, allocating multiple IP addresses tothe same wireless terminal is avoided.

Referring now to FIG. 5, an attach procedure 300 in accordance with oneimplementation is shown. A wireless network module such as wirelessterminal 302 attempts to attach to a network 304 that includes variousnetwork modules such as an MME 306, a serving SAE gateway 308, a PDN SAEgateway 310, a PCRF 312, and an HSS 314. The network 304 may include anexternal IP address allocation node 316. The wireless terminal 302transmits an attach request (i.e. a data packet that includes the attachrequest) to the MME 306. In one implementation, the attach requestincludes an indication of whether the wireless terminal 302 requires anIP address to be allocated during the attach procedure 300. As shown,the wireless terminal 302 includes a request for IP address allocationin the attach request. For example, the attach request may include adata packet, and the data packet may include a field associated with therequest IP address allocation. In this implementation, as shown, thewireless terminal 302 may include an integrated terminal that requiresIP address allocation during the attach procedure 300.

Upon authentication, an IP address is allocated to the wireless terminal302. For example, the MME 306 may transmit a create bearer contextrequest (e.g. a data packet that includes the create bearer contextrequest) to the PDN SAE gateway 310 that indicates that the wirelessterminal 302 requires an IP address. In response, the PDN SAE gateway310 allocates an IP address to the wireless terminal 302 and transmits acreate bearer context response (e.g. a data packet that includes thecreate bearer context response) to the MME 306. The MME 306 transmits anattach accept (e.g. a data packet that includes the attach accept),including the allocated IP address, to the wireless terminal 302. Thewireless terminal 302 completes the attach. Because the wirelessterminal 302 requested and received an IP address during the attachprocedure 300, the wireless terminal 302 does not request an IP addressusing other methods after the attach procedure 300. For example, thewireless terminal 302 does not require an IP address from the externalIP address allocation node 316.

Referring now to FIG. 6, an attach procedure 400 is shown in which thewireless terminal 302 includes a non-integrated terminal that does notrequire IP address allocation. The wireless terminal 302 transmits anattach request to the MME 306. In one implementation, the attach requestincludes an indication of whether the wireless terminal 302 requires anIP address to be allocated during the attach procedure 400. As shown,the wireless terminal 302 indicates, in the attach request, that IPaddress allocation is not required.

Upon authentication, the network 304 does not allocate an IP address tothe wireless terminal 302. For example, the MME 306 may transmit acreate bearer context request to the PDN SAE gateway 310 that indicatesthat the wireless terminal 302 does not require an IP address. Inresponse, the PDN SAE gateway 310 transmits a create bearer contextresponse to the MME 306 that indicates that an IP address was notallocated to the wireless terminal 302. The MME 306 transmits an attachaccept to the wireless terminal 302. The attach accept may include anyadditional information required for the wireless terminal 302 to obtainan IP address after the attach procedure 400. The wireless terminal 302completes the attach.

After the attach procedure, the wireless terminal 302 independentlyobtains an IP address. For example, the wireless terminal 302 maycommunicate with the external IP address allocation node 316 to obtainan IP address.

As described in FIG. 5, the network 304 allocates the IP address to thewireless terminal 302. Consequently, the network 304 knows the IPaddress of the wireless terminal 302. Conversely, the wireless terminal302 obtains an IP address via the external IP address allocation node316 and, as such, the network 304 does not know the IP address of thewireless terminal 302. As shown in FIG. 6, the wireless terminal 302 mayinitiate a bearer context modification step with the PDN SAE gateway 310to inform the network of the IP address of the wireless terminal 302.

Referring now to FIG. 7, a method 450 for attaching to a network 304begins in step 452. In step 454, the wireless terminal 302 transmits anattach request that includes an IP allocation preference to the network304. In step 456, the network 304 determines whether the wirelessterminal 302 requires IP allocation during the attach. If true, themethod 450 continues to step 458. If false, the method 450 continues tostep 460.

In step 458, the network 304 allocates an IP address to the wirelessterminal 302. In step 460, the network 304 accepts the attach. In step462, the wireless terminal 302 completes the attach. In step 464, thewireless terminal 302 determines whether the network 304 allocated an IPaddress during the attach. If true, the method 450 continues to step466. If false, the method 450 continues to step 468. In step 468, thewireless terminal 302 obtains an IP address via an alternative method,such as obtaining an IP address from the external IP address allocationnode 316. In step 470, the wireless terminal 302 modifies the bearercontext with the obtained IP address. The method ends in step 466.

Referring now to FIG. 8, the wireless terminal 302 does not indicatewhether IP address allocation is required during an attach procedure500. Instead, the network 304 may store data (e.g. subscriber datastored in a subscriber database) that indicates attributes of thewireless terminal 302. For example, subscriber data may include, but isnot limited to, a terminal type of the wireless terminal 302 and anindication of whether the wireless terminal 302 requires IP addressallocation. For example only, the HSS 314 may include the subscriberdatabase.

The wireless terminal 302 transmits an attach request to the MME 306.The attach request may not include an indication of whether the wirelessterminal 302 requires an IP address to be allocated during the attachprocedure 500. As shown, the wireless terminal 302 does not include arequest for IP address allocation in the attach request.

Upon authentication, the network 304 (e.g. via the HSS 314) retrievesthe subscriber data associated with the wireless terminal 302 from thesubscriber data base and transmits the subscriber data to the MME 306.As shown, the subscriber data for the wireless terminal 302 indicatesthat the wireless terminal 302 requires IP address allocation during theattach procedure 500. In response, the MME 306 may transmit a createbearer context request to the PDN SAE gateway 310 that indicates thatthe wireless terminal 302 requires an IP address based on the subscriberdata. The PDN SAE gateway 310 allocates an IP address to the wirelessterminal 302 and transmits a create bearer context response to the MME306. The MME 306 transmits an attach accept, including the allocated IPaddress, to the wireless terminal 302. The wireless terminal 302completes the attach. Because the wireless terminal 302 requested andreceived an IP address during the attach procedure 500, the wirelessterminal 302 does not request an IP address using other methods afterthe attach procedure 500.

Referring now to FIG. 9, the wireless terminal 302 does not indicatewhether IP address allocation is required during an attach procedure600. The wireless terminal 302 transmits an attach request to the MME306. The attach request may not include an indication of whether thewireless terminal 302 requires an IP address to be allocated during theattach procedure 600. As shown, the wireless terminal 302 does notinclude a request for IP address allocation in the attach request.

Upon authentication, the network 304 (e.g. via the HSS 314) retrievesthe subscriber data associated with the wireless terminal 302 from thesubscriber data base and transmits the subscriber data to the MME 306.As shown, the subscriber data for the wireless terminal 302 indicatesthat the wireless terminal 302 does not require IP address allocationduring the attach procedure 600. In response, the MME 306 may transmit acreate bearer context request to the PDN SAE gateway 310 that indicatesthat the wireless terminal 302 does not require an IP address based onthe subscriber data. The PDN SAE gateway 310 transmits a create bearercontext response to the MME 306 that indicates that an IP address wasnot allocated to the wireless terminal 302. The MME 306 transmits anattach accept to the wireless terminal 302. The attach accept mayinclude any additional information required for the wireless terminal302 to obtain an IP address after the attach procedure 600. The wirelessterminal 302 completes the attach.

After the attach procedure, the wireless terminal 302 independentlyobtains an IP address. For example, the wireless terminal 302 maycommunicate with the external IP address allocation node 316 to obtainan IP address. The wireless terminal 302 may initiate a bearer contextmodification step with the PDN SAE gateway 310 to inform the network ofthe IP address of the wireless terminal 302.

Referring now to FIG. 10, a method 650 for attaching to a network 304begins in step 652. In step 654, the wireless terminal 302 transmits anattach request that does not include an IP allocation preference to thenetwork 304. In step 656, the network 304 determines whether thewireless terminal 302 requires IP allocation during the attach based onsubscriber data. If true, the method 650 continues to step 658. Iffalse, the method 650 continues to step 660.

In step 658, the network 304 allocates an IP address to the wirelessterminal 302. In step 660, the network 304 accepts the attach. In step662, the wireless terminal 302 completes the attach. In step 664, thewireless terminal 302 determines whether the network 304 allocated an IPaddress during the attach. If true, the method 650 continues to step666. If false, the method 650 continues to step 668. In step 668, thewireless terminal 302 obtains an IP address via an alternative method,such as obtaining an IP address from the external IP address allocationnode 316. In step 670, the wireless terminal 302 modifies the bearercontext with the obtained IP address. The method ends in step 666.

Referring now to FIGS. 11A-11G, various exemplary implementationsincorporating the teachings of the present disclosure are shown.

Referring now to FIG. 11A, the teachings of the disclosure can beimplemented in an I/O interface 815 of a hard disk drive (HDD) 800. TheHDD 800 includes a hard disk assembly (HDA) 801 and an HDD printedcircuit board (PCB) 802. The HDA 801 may include a magnetic medium 803,such as one or more platters that store data, and a read/write device804. The read/write device 804 may be arranged on an actuator arm 805and may read and write data on the magnetic medium 803. Additionally,the HDA 801 includes a spindle motor 806 that rotates the magneticmedium 803 and a voice-coil motor (VCM) 807 that actuates the actuatorarm 805. A preamplifier device 808 amplifies signals generated by theread/write device 804 during read operations and provides signals to theread/write device 804 during write operations.

The HDD PCB 802 includes a read/write channel module (hereinafter, “readchannel”) 809, a hard disk controller (HDC) module 810, a buffer 811,nonvolatile memory 812, a processor 813, and a spindle/VCM driver module814. The read channel 809 processes data received from and transmittedto the preamplifier device 808. The HDC module 810 controls componentsof the HDA 801 and communicates with an external device (not shown) viathe I/O interface 815. The external device may include a computer, amultimedia device, a mobile computing device, etc. The I/O interface 815may include wireline and/or wireless communication links.

The HDC module 810 may receive data from the HDA 801, the read channel809, the buffer 811, nonvolatile memory 812, the processor 813, thespindle/VCM driver module 814, and/or the I/O interface 815. Theprocessor 813 may process the data, including encoding, decoding,filtering, and/or formatting. The processed data may be output to theHDA 801, the read channel 809, the buffer 811, nonvolatile memory 812,the processor 813, the spindle/VCM driver module 814, and/or the I/Ointerface 815.

The HDC module 810 may use the buffer 811 and/or nonvolatile memory 812to store data related to the control and operation of the HDD 800. Thebuffer 811 may include DRAM, SDRAM, etc. Nonvolatile memory 812 mayinclude any suitable type of semiconductor or solid-state memory, suchas flash memory (including NAND and NOR flash memory), phase changememory, magnetic RAM, and multi-state memory, in which each memory cellhas more than two states. The spindle/VCM driver module 814 controls thespindle motor 806 and the VCM 807. The HDD PCB 802 includes a powersupply 816 that provides power to the components of the HDD 800.

Referring now to FIG. 11B, the teachings of the disclosure can beimplemented in an I/O interface 829 of a DVD drive 818 or of a CD drive(not shown). The DVD drive 818 includes a DVD PCB 819 and a DVD assembly(DVDA) 820. The DVD PCB 819 includes a DVD control module 821, a buffer822, nonvolatile memory 823, a processor 824, a spindle/FM (feed motor)driver module 825, an analog front-end module 826, a write strategymodule 827, and a DSP module 828.

The DVD control module 821 controls components of the DVDA 820 andcommunicates with an external device (not shown) via the I/O interface829. The external device may include a computer, a multimedia device, amobile computing device, etc. The I/O interface 829 may include wirelineand/or wireless communication links.

The DVD control module 821 may receive data from the buffer 822,nonvolatile memory 823, the processor 824, the spindle/FM driver module825, the analog front-end module 826, the write strategy module 827, theDSP module 828, and/or the I/O interface 829. The processor 824 mayprocess the data, including encoding, decoding, filtering, and/orformatting. The DSP module 828 performs signal processing, such as videoand/or audio coding/decoding. The processed data may be output to thebuffer 822, nonvolatile memory 823, the processor 824, the spindle/FMdriver module 825, the analog front-end module 826, the write strategymodule 827, the DSP module 828, and/or the I/O interface 829.

The DVD control module 821 may use the buffer 822 and/or nonvolatilememory 823 to store data related to the control and operation of the DVDdrive 818. The buffer 822 may include DRAM, SDRAM, etc. Nonvolatilememory 823 may include any suitable type of semiconductor or solid-statememory, such as flash memory (including NAND and NOR flash memory),phase change memory, magnetic RAM, and multi-state memory, in which eachmemory cell has more than two states. The DVD PCB 819 includes a powersupply 830 that provides power to the components of the DVD drive 818.

The DVDA 820 may include a preamplifier device 831, a laser driver 832,and an optical device 833, which may be an optical read/write (ORW)device or an optical read-only (OR) device. A spindle motor 834 rotatesan optical storage medium 835, and a feed motor 836 actuates the opticaldevice 833 relative to the optical storage medium 835.

When reading data from the optical storage medium 835, the laser driverprovides a read power to the optical device 833. The optical device 833detects data from the optical storage medium 835, and transmits the datato the preamplifier device 831. The analog front-end module 826 receivesdata from the preamplifier device 831 and performs such functions asfiltering and A/D conversion. To write to the optical storage medium835, the write strategy module 827 transmits power level and timing datato the laser driver 832. The laser driver 832 controls the opticaldevice 833 to write data to the optical storage medium 835.

Referring now to FIG. 11C, the teachings of the disclosure can beimplemented in a network interface 843 of a high definition television(HDTV) 837. The HDTV 837 includes an HDTV control module 838, a display839, a power supply 840, memory 841, a storage device 842, the networkinterface 843, and an external interface 845. If the network interface843 includes a wireless local area network interface, an antenna (notshown) may be included.

The HDTV 837 can receive input signals from the network interface 843and/or the external interface 845, which can send and receive data viacable, broadband Internet, and/or satellite. The HDTV control module 838may process the input signals, including encoding, decoding, filtering,and/or formatting, and generate output signals. The output signals maybe communicated to one or more of the display 839, memory 841, thestorage device 842, the network interface 843, and the externalinterface 845.

Memory 841 may include random access memory (RAM) and/or nonvolatilememory. Nonvolatile memory may include any suitable type ofsemiconductor or solid-state memory, such as flash memory (includingNAND and NOR flash memory), phase change memory, magnetic RAM, andmulti-state memory, in which each memory cell has more than two states.The storage device 842 may include an optical storage drive, such as aDVD drive, and/or a hard disk drive (HDD). The HDTV control module 838communicates externally via the network interface 843 and/or theexternal interface 845. The power supply 840 provides power to thecomponents of the HDTV 837.

Referring now to FIG. 11D, the teachings of the disclosure may beimplemented in a network interface 852 of a vehicle 846. The vehicle 846may include a vehicle control system 847, a power supply 848, memory849, a storage device 850, and the network interface 852. If the networkinterface 852 includes a wireless local area network interface, anantenna (not shown) may be included. The vehicle control system 847 maybe a powertrain control system, a body control system, an entertainmentcontrol system, an anti-lock braking system (ABS), a navigation system,a telematics system, a lane departure system, an adaptive cruise controlsystem, etc.

The vehicle control system 847 may communicate with one or more sensors854 and generate one or more output signals 856. The sensors 854 mayinclude temperature sensors, acceleration sensors, pressure sensors,rotational sensors, airflow sensors, etc. The output signals 856 maycontrol engine operating parameters, transmission operating parameters,suspension parameters, braking parameters, etc.

The power supply 848 provides power to the components of the vehicle846. The vehicle control system 847 may store data in memory 849 and/orthe storage device 850. Memory 849 may include random access memory(RAM) and/or nonvolatile memory. Nonvolatile memory may include anysuitable type of semiconductor or solid-state memory, such as flashmemory (including NAND and NOR flash memory), phase change memory,magnetic RAM, and multi-state memory, in which each memory cell has morethan two states. The storage device 850 may include an optical storagedrive, such as a DVD drive, and/or a hard disk drive (HDD). The vehiclecontrol system 847 may communicate externally using the networkinterface 852.

Referring now to FIG. 11E, the teachings of the disclosure can beimplemented in a cellular network interface 867 and/or a networkinterface 868 of a cellular phone 858. The cellular phone 858 includes aphone control module 860, a power supply 862, memory 864, a storagedevice 866, and the cellular network interface 867. The cellular phone858 may include the network interface 868, a microphone 870, an audiooutput 872 such as a speaker and/or output jack, a display 874, and auser input device 876 such as a keypad and/or pointing device. If thenetwork interface 868 includes a wireless local area network interface,an antenna (not shown) may be included.

The phone control module 860 may receive input signals from the cellularnetwork interface 867, the network interface 868, the microphone 870,and/or the user input device 876. The phone control module 860 mayprocess signals, including encoding, decoding, filtering, and/orformatting, and generate output signals. The output signals may becommunicated to one or more of memory 864, the storage device 866, thecellular network interface 867, the network interface 868, and the audiooutput 872.

Memory 864 may include random access memory (RAM) and/or nonvolatilememory. Nonvolatile memory may include any suitable type ofsemiconductor or solid-state memory, such as flash memory (includingNAND and NOR flash memory), phase change memory, magnetic RAM, andmulti-state memory, in which each memory cell has more than two states.The storage device 866 may include an optical storage drive, such as aDVD drive, and/or a hard disk drive (HDD). The power supply 862 providespower to the components of the cellular phone 858.

Referring now to FIG. 11F, the teachings of the disclosure can beimplemented in a network interface 885 of a set top box 878. The set topbox 878 includes a set top control module 880, a display 881, a powersupply 882, memory 883, a storage device 884, and the network interface885. If the network interface 885 includes a wireless local area networkinterface, an antenna (not shown) may be included.

The set top control module 880 may receive input signals from thenetwork interface 885 and an external interface 887, which can send andreceive data via cable, broadband Internet, and/or satellite. The settop control module 880 may process signals, including encoding,decoding, filtering, and/or formatting, and generate output signals. Theoutput signals may include audio and/or video signals in standard and/orhigh definition formats. The output signals may be communicated to thenetwork interface 885 and/or to the display 881. The display 881 mayinclude a television, a projector, and/or a monitor.

The power supply 882 provides power to the components of the set top box878. Memory 883 may include random access memory (RAM) and/ornonvolatile memory. Nonvolatile memory may include any suitable type ofsemiconductor or solid-state memory, such as flash memory (includingNAND and NOR flash memory), phase change memory, magnetic RAM, andmulti-state memory, in which each memory cell has more than two states.The storage device 884 may include an optical storage drive, such as aDVD drive, and/or a hard disk drive (HDD).

Referring now to FIG. 11G, the teachings of the disclosure can beimplemented in a network interface 894 of a mobile device 889. Themobile device 889 may include a mobile device control module 890, apower supply 891, memory 892, a storage device 893, the networkinterface 894, and an external interface 899. If the network interface894 includes a wireless local area network interface, an antenna (notshown) may be included.

The mobile device control module 890 may receive input signals from thenetwork interface 894 and/or the external interface 899. The externalinterface 899 may include USB, infrared, and/or Ethernet. The inputsignals may include compressed audio and/or video, and may be compliantwith the MP3 format. Additionally, the mobile device control module 890may receive input from a user input 896 such as a keypad, touchpad, orindividual buttons. The mobile device control module 890 may processinput signals, including encoding, decoding, filtering, and/orformatting, and generate output signals.

The mobile device control module 890 may output audio signals to anaudio output 897 and video signals to a display 898. The audio output897 may include a speaker and/or an output jack. The display 898 maypresent a graphical user interface, which may include menus, icons, etc.The power supply 891 provides power to the components of the mobiledevice 889. Memory 892 may include random access memory (RAM) and/ornonvolatile memory.

Nonvolatile memory may include any suitable type of semiconductor orsolid-state memory, such as flash memory (including NAND and NOR flashmemory), phase change memory, magnetic RAM, and multi-state memory, inwhich each memory cell has more than two states. The storage device 893may include an optical storage drive, such as a DVD drive, and/or a harddisk drive (HDD). The mobile device may include a personal digitalassistant, a media player, a laptop computer, a gaming console, or othermobile computing device.

The broad teachings of the disclosure can be implemented in a variety offorms. For example, one or more techniques discussed above may beapplicable to other types of wireless networks (e.g. 3GPP LTE and WiMAXwireless networks). Therefore, while this disclosure includes particularexamples, the true scope of the disclosure should not be so limitedsince other modifications will become apparent to the skilledpractitioner upon a study of the drawings, the specification, and thefollowing claims.

1. A networking system, comprising: a first wireless network module thattransmits a request to attach to a network; and a second wirelessnetwork module that: receives the request; determines whether the firstwireless network module requires an IP address based on the request; andselectively allocates an IP address to the first wireless network modulebased on the determination.
 2. The networking system of claim 1,wherein: the request includes an indication that the first wirelessnetwork module requires an IP address; and the second wireless networkmodule allocates an IP address to the first wireless network modulebased on the request.
 3. The networking system of claim 1, wherein: therequest includes an indication that the first wireless network moduledoes not require an IP address; and the second wireless network moduledoes not allocate an IP address to the first wireless network module. 4.The networking system of claim 3, wherein: the first wireless networkmodule attaches to the network without receiving an IP address; andafter attaching to the network, the first wireless network moduleobtains an IP address from a third wireless network module.
 5. Thenetworking system of claim 4, wherein the first wireless network modulemodifies a bearer context based on the IP address obtained from thethird wireless network module.
 6. The networking system of claim 1,wherein the second wireless network module retrieves subscriber dataassociated with the first wireless network module based on the request.7. The networking system of claim 6, further comprising a database thatstores the subscriber data.
 8. The networking system of claim 6, whereinthe second wireless network module determines whether to allocate an IPaddress to the first wireless network module based on the subscriberdata.
 9. The networking system of claim 8, wherein the subscriber dataindicates whether the first wireless network module is one of anintegrated wireless terminal and a non-integrated wireless terminal. 10.The networking system of claim 8, wherein the subscriber data indicateswhether the first wireless network module requires IP address allocationduring an attach procedure.
 11. The networking system of claim 1,wherein the network comprises a 3^(rd) Generation Partnership Project(3GPP) evolved wireless network.
 12. The networking system of claim 1,wherein the first wireless network module comprises at least one of amobile telephone and a laptop computer.
 13. The networking system ofclaim 1, wherein the second wireless network module comprises at leastone of a mobility management entity (MME), a gateway, and a homesubscriber server (HSS) in a 3^(rd) Generation Partnership Project(3GPP) evolved wireless network.
 14. The networking system of claim 1,wherein the second wireless network module creates a bearer contextrequest that indicates whether the first wireless network modulerequires IP address allocation.
 15. A networking method, comprising:transmitting a request to attach to a network from a first wirelessnetwork module; receiving the request at a second wireless networkmodule; determining whether the first wireless network module requiresan IP address based on the request; and selectively allocating an IPaddress to the first wireless network module based on the determination.16. The method of claim 15, wherein the request includes an indicationthat the wireless network module requires an IP address, and furthercomprising allocating an IP address to the first wireless network modulebased on the request.
 17. The method of claim 15, wherein: the requestincludes an indication that the wireless network module does not requirean IP address; and the first wireless network module is not allocated anIP address.
 18. The method of claim 17, wherein: the first wirelessnetwork module attaches to the network without receiving an IP address;and after attaching to the network, the first wireless network moduleobtains an IP address from a third wireless network module.
 19. Themethod of claim 18, further comprising modifying a bearer context basedon the IP address obtained from the third wireless network module. 20.The method of claim 15, further comprising retrieving subscriber dataassociated with the first wireless network module based on the request.21. The method of claim 20, further comprising storing the subscriberdata in a database.
 22. The method of claim 20, further comprisingdetermining whether to allocate an IP address to the first wirelessnetwork module based on the subscriber data.
 23. The method of claim 22,wherein the subscriber data indicates whether the first wireless networkmodule is one of an integrated wireless terminal and a non-integratedwireless terminal.
 24. The method of claim 22, wherein the subscriberdata indicates whether the first wireless network module requires IPaddress allocation during an attach procedure.
 25. The method of claim15, wherein the network comprises a 3^(rd) Generation PartnershipProject (3GPP) evolved wireless network.
 26. The method of claim 15,wherein the first wireless network module comprises at least one of amobile telephone and a laptop computer.
 27. The method of claim 15,wherein the second wireless network module comprises at least one of amobility management entity (MME), a gateway, and a home subscriberserver (HSS) in a 3^(rd) Generation Partnership Project (3GPP) evolvedwireless network.
 28. The method of claim 15, further comprisingcreating a bearer context request that indicates whether the firstwireless network module requires IP address allocation.